Hi David, I don't know what that could be and I haven't heard of it before. Goggling shows many problems with W8 touchpad freezing. I assume you just connect KFLOP without running any of our software and it freezes? Maybe W8.1 thinks KFLOP is a mouse? Have you been able to load our driver? What does Device Manager Show KFLOP as? Here is a link I found from Microsoft but I wouldn't have high expectations. http://answers.microsoft.com/en-us/windows/forum/windows_8-hardware/touch-pad-becomes-inactive-and-pointer-freezes-on/7247834e-fe06-458f-afcb-8e34799343f1?page=2
Regards TK
Group: DynoMotion |
Message: 8970 |
From: David Stevenson |
Date: 1/25/2014 |
Subject: Re: KFlop Freezes System Pointer |
Hi Tom,
There were issues to get the driver installed initially, but was
able to by disabling signature checking in W8. Device manager shows
KFlop properly as a known device 4.XX
The pointer worked at first, but when I ran my brushless startup
file, the pointer remained welded after that until I removed the USB
connection to KFlop. I don't think I rebooted after that, so I will
go try adding the Konnect code and run through it again.
Thanks for your help and the link,
David.
*************************
On 1/25/2014 3:46 PM, Tom Kerekes
wrote:
Hi David,
I don't know what that could be and I haven't heard of it
before. Goggling shows many problems with W8 touchpad
freezing.
I assume you just connect KFLOP without running any of our
software and it freezes? Maybe W8.1 thinks KFLOP is a
mouse? Have you been able to load our driver? What does
Device Manager Show KFLOP as?
Here is a link I found from Microsoft but I wouldn't have
high expectations.
http://answers.microsoft.com/en-us/windows/forum/windows_8-hardware/touch-pad-becomes-inactive-and-pointer-freezes-on/7247834e-fe06-458f-afcb-8e34799343f1?page=2
Regards
TK
Group: DynoMotion |
Message: 8990 |
From: daveymahomh600e |
Date: 1/26/2014 |
Subject: Re: KFlop Freezes System Pointer |
Hi Tom,
I'll try to explain what is happening... KMotion loads and runs fine until I process a c program. The program executes and finishes, but then the pointer is frozen. If I disconnect KFLOP and reconnect the pointer is fine.
I have a 3phasebrushlessstartup.c file to initialize the drives. Running it affects the pointer in the manner noted above. I tried adding the Konnect code to it, at the top just inside the main bracket, but when the file processes it disconnects KFLOP, puts a window up showing "Read failed - auto disconnect" but then reconnects within a few seconds. The pointer then is fine, but the code has been dumped from KFLOP because of the disconnect.
Any suggestions? Again, the system is 64bit W8.1
Thanks, David.
|
|
Group: DynoMotion |
Message: 8991 |
From: Tom Kerekes |
Date: 1/26/2014 |
Subject: Re: KFlop Freezes System Pointer |
Hi David,
It sounds to me more like a noise problem rather than a software/driver problem because it only happens after you enable your SnapAmp Axes and the 80V (or whatever) starts switching on all your motor wiring and such. Is this correct. You could try an experiment where you run the same c file that causes the freeze but with high voltage supplies turned off to see if you still get the freeze or not.
Also if this is a laptop try running on battery for full isolation.
Regarding the Konnect: Try running the EnableKonnect.c example by itself and check if Konnect works correctly in that there is no error on the Console Screen, and you can toggle Output 48 on the Digital IO Screen to Toggle the Output LED 0 on Konnect.
Regards TK
Group: DynoMotion |
Message: 8993 |
From: David Stevenson |
Date: 1/26/2014 |
Subject: Re: KFlop Freezes System Pointer |
Hi Tom,
It looks like there may be a noise issue. Running with just the
laptop allows the Konnect to load and toggle.
I did see a new error when trying to run the brushless startup with
the Konnect code and the main power on... "COMM ERROR AUX1
(signature not A5). Does that yield any other clues?
Thanks,
David.
*****************
On 1/26/2014 1:39 PM, Tom Kerekes
wrote:
Hi David,
It sounds to me
more like a noise problem rather than a
software/driver problem because it only happens after
you enable your SnapAmp Axes and the 80V (or whatever)
starts switching on all your motor wiring and such.
Is this correct. You could try an experiment where
you run the same c file that causes the freeze but
with high voltage supplies turned off to see if you
still get the freeze or not.
Also if this is a
laptop try running on battery for full isolation.
Regarding the
Konnect: Try running the EnableKonnect.c example by
itself and check if Konnect works correctly in that
there is no error on the Console Screen, and you can
toggle Output 48 on the Digital IO Screen to Toggle
the Output LED 0 on Konnect.
Regards
TK
Group: DynoMotion |
Message: 8995 |
From: Tom Kerekes |
Date: 1/26/2014 |
Subject: Re: KFlop Freezes System Pointer |
Hi David,
COMM ERROR AUX1 (signature not A5) means that there was a communication error with KFLOP communicating with Konnect. Every 180us KFLOP reads/writes all the IO from Konnect including a fixed 8-bit signature of Hex A5. If the A5 is not read properly this error is displayed and Konnect is disabled.
Does this happen right away? Or after a while? Are you turning on Konnect in the example program before running the brushless startup or within it? How long is your ribbon cable to Konnect?
Regards TK
Group: DynoMotion |
Message: 8996 |
From: David Stevenson |
Date: 1/26/2014 |
Subject: Re: KFlop Freezes System Pointer |
Hi Tom,
The error occurred while trying to run the brushless file... I
clicked the save/compile and the KFLOP disconnected and then
reconnected, clicked again, same outcome, clicked again and the
error showed up in the console window on about the third go around.
Once the Konnect is disabled will it try to reconnect?
The ribbon is about 12 inches in this machine. There is no way to
make it any shorter.
Thanks,
David.
********************
On 1/26/2014 3:04 PM, Tom Kerekes
wrote:
Hi David,
COMM ERROR AUX1
(signature not A5) means that there was a communication
error with KFLOP communicating with Konnect. Every
180us KFLOP reads/writes all the IO from Konnect
including a fixed 8-bit signature of Hex A5. If the A5
is not read properly this error is displayed and Konnect
is disabled.
Does this happen right
away? Or after a while? Are you turning on Konnect in
the example program before running the brushless startup
or within it? How long is your ribbon cable to Konnect?
Regards
TK
Group: DynoMotion |
Message: 8997 |
From: Tom Kerekes |
Date: 1/26/2014 |
Subject: Re: KFlop Freezes System Pointer |
Hi David,
Regarding if Konnect will try to re-connect: basically no. It isn't really a matter of "a connection" rather whether it is being "serviced". When a board is "added" to an Aux port then KFLOP will service the board until there is an error. To resume servicing Konnect the two lines of code would need to be re-executed to clear the Aux Port and re-add the board.
I'm confused on what you are doing with regarding to connections, power, and coding. I think there might be two problems. One being SnapAmp/noise/disconnects and another with Konnect/COMM Errors. Let's go back to square one and go one step at a time. Remove Konnect completely - hardware and any code. Does your brushless file run and work with motor power on correctly? Regards TK
Group: DynoMotion |
Message: 8998 |
From: David Stevenson |
Date: 1/26/2014 |
Subject: Re: KFlop Freezes System Pointer |
Hi Tom,
It seems to run correctly, but the screen pointer is frozen
afterwards and I can't do anything without the pointer. My brushless
code outputs to the console that the axis are ready to go.
If I then disconnect the motor power, the pointer releases. If the
motor power is turned on again, the pointer freezes again.
Thanks for your help,
David.
*********************
On 1/26/2014 3:47 PM, Tom Kerekes
wrote:
Hi David,
Regarding if Konnect
will try to re-connect: basically no. It isn't really a
matter of "a connection" rather whether it is being
"serviced". When a board is "added" to an Aux port then
KFLOP will service the board until there is an error.
To resume servicing Konnect the two lines of code would
need to be re-executed to clear the Aux Port and re-add
the board.
I'm confused on what you are doing with regarding to
connections, power, and coding.
I think there might be two problems. One being
SnapAmp/noise/disconnects and another with Konnect/COMM
Errors.
Let's go back to square one and go one step at a time.
Remove Konnect completely - hardware and any code.
Does your brushless file run and work with motor power on
correctly?
Regards
TK
Group: DynoMotion |
Message: 8999 |
From: Tom Kerekes |
Date: 1/26/2014 |
Subject: Re: KFlop Freezes System Pointer |
H David,
ok we need to resolve this before going forward.
You don't have a USB mouse? Or use the keyboard? That would allow us to see what else is working
and what is not working while the touchpad is frozen.
So it seems switching noise from SnapAmp/Motor wiring is causing the touchpad to freeze.
It seems strange that noise through the KFLOP USB cable would affect the touchpad but not the KFLOP communication.
I suppose we would need to have all the info on your wiring, grounding, shielding, etc... Maybe you could come up with some experiments yourself to track it down?
I don't know if internally to the laptop the touchpad is USB?
It appears switching noise is entering through the USB cable into the Laptop and disturbing the touchpad?
What if you leave motor power on but unplug the USB cable from the laptop? (I think you said before this releases the touchpad?) What about if you unplug the end at KFLOP and leave the free cable plugged into the laptop?
Regards TK
Group: DynoMotion |
Message: 9001 |
From: David Stevenson |
Date: 1/26/2014 |
Subject: Re: KFlop Freezes System Pointer |
Hi Tom,
I plugged in a USB mouse and it still works when the touchpad is
frozen, as does the keyboard. That lets me move around, which is
great, and I can deal with the touchpad later.
What I did was run the brushless file, with the Konnect code removed
and it seemed to work fine. I could upload the channels as expected
in the console. Next I loaded the Konnect and it worked properly
too... I could toggle #48. Then I tried running the brushless file
again and the KFLOP disconnected and then reconnected as previously
noted. I also tried including the Konnect in the brushless file, but
KFLOP disconnected and then reconnected as before.
Your thoughts?
Thanks,
David.
*******************
On 1/26/2014 4:49 PM, Tom Kerekes
wrote:
H David,
ok we need to
resolve this before going forward.
You don't have a
USB mouse? Or use the keyboard? That would allow us
to see what else is working and what is not working
while the touchpad is frozen.
So it seems
switching noise from SnapAmp/Motor wiring is causing
the touchpad to freeze.
It seems strange that
noise through the KFLOP USB cable would affect the
touchpad but not the KFLOP communication.
I suppose we
would need to have all the info on your wiring,
grounding, shielding, etc... Maybe you could come up
with some experiments yourself to track it down?
I don't know if
internally to the laptop the touchpad is USB?
It appears
switching noise is entering through the USB cable into
the Laptop and disturbing the touchpad?
What if you leave
motor power on but unplug the USB cable from the
laptop? (I think you said before this releases the
touchpad?) What about if you unplug the end at KFLOP
and leave the free cable plugged into the laptop?
Regards
TK
Group: DynoMotion |
Message: 9003 |
From: Tom Kerekes |
Date: 1/26/2014 |
Subject: Re: KFlop Freezes System Pointer |
Hi David,
The Reset signal in the 1 foot long ribbon cable may be picking up noise and crosstalk and causing KFLOP to reset.
Were you aware of this issue?
See this post on adding a filter capacitor:
http://groups.yahoo.com/neo/groups/DynoMotion/conversations/messages/8541
Regards TK
Group: DynoMotion |
Message: 9005 |
From: David Stevenson |
Date: 1/26/2014 |
Subject: Re: KFlop Freezes System Pointer |
Hi Tom,
I know you had recommended keeping the ribbon as short as possible.
Didn't realize the filter might have to be added. Any plans to add
shielded cables anywhere down the road? It's easier (and maybe less
expensive) for a non-electronic guy like me to stick to din relays
and not risk frying an expensive board.
Thanks,
David.
*********************
On 1/26/2014 6:06 PM, Tom Kerekes
wrote:
Hi David,
The Reset signal
in the 1 foot long ribbon cable may be picking up
noise and crosstalk and causing KFLOP to reset.
Were you aware of
this issue? See this post on adding a filter
capacitor:
Regards
TK
Group: DynoMotion |
Message: 9006 |
From: Tom Kerekes |
Date: 1/26/2014 |
Subject: Re: KFlop Freezes System Pointer |
Hi David,
The next rev 1.3 of KFLOP will have a filter cap on reset and should no longer have this issue.
Regards TK
Group: DynoMotion |
Message: 9007 |
From: David Stevenson |
Date: 1/26/2014 |
Subject: Re: KFlop Freezes System Pointer |
Hi Tom,
When will you start shipping those?
Thanks again,
David.
******************
On 1/26/2014 7:33 PM, Tom Kerekes
wrote:
Hi David,
The next rev 1.3
of KFLOP will have a filter cap on reset and should no
longer have this issue.
Regards
TK
Group: DynoMotion |
Message: 9008 |
From: Tom Kerekes |
Date: 1/26/2014 |
Subject: Re: KFlop Freezes System Pointer |
Hi David, Probably not for several months. Regards TK
Group: DynoMotion |
Message: 9009 |
From: daveymahomh600e |
Date: 1/27/2014 |
Subject: Re: KFlop Freezes System Pointer |
Hi Tom, The earlier posts talk about adding the capacitor. Could you lend some guidance to a non-electronic guy on how to put one between those pins?
Thanks, David.
|
|
Group: DynoMotion |
Message: 9011 |
From: Tom Kerekes |
Date: 1/27/2014 |
Subject: Re: KFlop Freezes System Pointer |
Hi David, The simplest method is to add an extra connector on a ribbon cable to either J4, J6, or J7 (on the KFLOP end). Then insert a 0.001uF (same values as 1000pF) ceramic capacitor into the connector socket between Reset (JP6 pin 4 and GND pin8). The capacitor is unpolarized and can be connected either way. See attached photo. Additional Link Here
Here is a link to a Digikey source. Another option would be to have a very short cable to a breakout board and attach it there. Or place a Konnect very close to KFLOP. HTH Regards TK
Group: DynoMotion |
Message: 9012 |
From: David Stevenson |
Date: 1/27/2014 |
Subject: Re: KFlop Freezes System Pointer [1 Attachment] |
Hi Tom,
I think even I could do that... but first an uneducated question...
I happen to have a 0.01uF capacitor (it's a long story) and was
wondering if I can use that?
Thank you very much!
David
*****************
On 1/27/2014 12:29 PM, Tom Kerekes
wrote:
Hi David,
The simplest method is to add an extra connector on a
ribbon cable to either J4, J6, or J7 (on the KFLOP end).
Then insert a 0.001uF (same values as 1000pF) ceramic
capacitor into the connector socket between Reset (JP6 pin
4 and GND pin8). The capacitor is unpolarized and can be
connected either way. See attached photo. Additional
Link Here
Here is a link to a Digikey
source.
Another option would be to have a very short cable to a
breakout board and attach it there.
Or place a Konnect very close to KFLOP.
HTH
Regards
TK
Group: DynoMotion |
Message: 9013 |
From: Tom Kerekes |
Date: 1/27/2014 |
Subject: Re: KFlop Freezes System Pointer |
Hi David,
0.01uF should work also.
Regards TK
Group: DynoMotion |
Message: 9014 |
From: David Stevenson |
Date: 1/27/2014 |
Subject: Re: KFlop Freezes System Pointer |
That's grrrrrreat!!!
Thanks Tom!
David
****************
On 1/27/2014 12:53 PM, Tom Kerekes
wrote:
Hi David,
0.01uF should
work also.
Regards
TK
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |